-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(cassandra-stress): bump c-s version to 3.17.0 #9296
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
there was an ask, to first test it to see if it elevate any of the issues observed |
@fruch could you propose owner and the the specific issue? |
I'm trying it for https://github.com/scylladb/scylla-enterprise/issues/4946 @juliayakovlev would be trying it for https://github.com/scylladb/scylla-enterprise/issues/4504 |
Read & mixed test - the issue is reproduced: Write load - it was not happened with previous cassandra-stress version and is not happened with |
please report those finding in: |
@CodeLieutenant 3.16.0 doesn't have scylladb/cassandra-stress#32 in it. can you please release a new c-s version that would include it ? |
Sorry my mistake, I thought it was released with 3.16. |
3c5bc69
to
0c659c7
Compare
0c659c7
to
d96f633
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
060696c
to
03c7a2b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
so scylladb/cassandra-stress#32, wasn't fixing any of the issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I think this one get's fixed: scylladb/scylladb#19107 |
I would guess it wouldn't did anyone rerun it with this one ? |
see https://github.com/scylladb/scylla-enterprise/issues/4504#issuecomment-2495859043 - results don't show imbalance anymore (just latency and throughput issues for read and mixed scenarios) |
The issue is about latency, and that run proves that the imbalance is not the cause of latency issues. I.e. it seems to not be that critical |
bump c-s version to 3.17.0
Main reason for version change:
Switch to ReplicaOrdering.RANDOM for select LBPs 32
Other Noticable Changes since the last version used in SCT:
Testing
PR pre-checks (self review)
backport
labels